Testing apparatus and testing method

ABSTRACT

A testing apparatus for evaluating operations by software installed in a mobile terminal includes a scenario setting unit for setting a scenario including operation information for executing functions that are performed by the mobile terminal, an operation determining unit for determining whether an operation indicated by the operation information included in the scenario is influenced by a device installed in the mobile terminal, an operation target converting unit for converting the operation determined to be influenced by the device installed in the mobile terminal according to the device installed in the mobile terminal, a scenario executing unit for executing the scenario set by the scenario setting unit according to the operation converted by the operation target converting unit, and a scenario execution result determining unit for determining whether an execution result of the scenario executed by the scenario execution unit is the same as a result assumed in advance.

TECHNICAL FIELD

The present invention relates to a testing apparatus for a mobileterminal.

BACKGROUND ART

Because of its functional advancement, operation procedures of a mobileterminal have become more complicated. And with the advancement infunctionalities, operation steps for executing a function have alsoincreased. Furthermore, the volume of software to be stored in a mobileterminal is also increasing. With the increase in software volume, thenumber of defects is also increasing. Regarding these defects, it ispractically impossible to detect them all beforehand. Thereforeevaluating software installed in a mobile terminal has been performed.

For example, an evaluating method using an automated evaluation tool isknown. In order to use the evaluation method of the automated evaluationtool, it is necessary for software installed in the target mobileterminal to include, as one of operation methods of the software,predefined operation procedures. Furthermore, it is necessary for a userto be able to use desired functions by pressing menu buttons or bypressing ten key buttons.

An evaluation method using an automated evaluation tool includes afunctional method. In the functional method, a specific function of amobile terminal is evaluated by a predefined operation procedure. Byevaluating a specific function, it is possible to check if the specificfunction of software installed in a mobile terminal functions properlyin accordance with the required specifications.

For example, in the case where a specific function of a mobile terminalthat includes an input device such as a touch panel, etc., is evaluated,there is a case in which a process corresponding to the pressing of acertain icon displayed in the touch panel is performed according to acertain scenario. In this case, an area for the certain icon to beselected is specified, and the process corresponding to the pressing ofa certain position included in the area is performed by an automatedevaluation tool. By having the process for the pressing of a certainicon performed by the automated evaluation tool, it is determinedwhether the process performed by the pressing meets requiredspecifications or not.

For example, a method of non-linear corrections in touch screens isknown (e.g., refer to patent document 1).

RELATED ART DOCUMENT

-   [Patent Document 1] Japanese Patent Application Publication No.    2005-539325

SUMMARY OF THE INVENTION Problem to be Solved by the Invention

There is a case where a function targeted for evaluation cannot beperformed by the same operation due to the difference of the deviceincluded in the mobile terminal.

For example, there is a case where sizes or resolutions of outputscreens are different among mobile terminals (apparatuses). That is,sometimes, for each mobile terminal (each apparatus), an installeddevice is different. In the case of an input of a touch panel method,the size or the resolution of the screen is different depending on thedevice.

In an automated evaluation tool, in order to make it universal, takingadvantage of coordinates, it is often the case that operation commandsthat include a command specifying a certain location of a display screenare created. For example, taking advantage of X-Y coordinates, operationcommands that include a command specifying a certain location of adisplay screen are created. Also, in a scenario created for evaluating acertain function, operation commands that include a command specifying acertain location of a display screen are included.

Therefore, there is a case where once a scenario is created, due to adevice dependency, the scenario cannot be used with other mobileterminals (apparatuses). The reason is that there is a case where,depending on the size or the resolution of the screen, locations (X-Ycoordinates) where parts are installed are different. The reason is thatthere is a case where operation commands created based on coordinates ofinstalling locations of software parts, such as buttons, for operating aspecific function are included in a scenario.

Therefore, regarding scenarios created by an automated evaluation tool,the scenarios' re-usability for other apparatuses becomes low except forthe apparatus for which the scenarios are created.

To be more precise, the size and the resolution of the touch panelincluded in mobile terminals varies. Therefore, an area for a certainicon to be selected is needed to be specified for each size or eachresolution of the touch panel included in mobile terminals. That is, theautomated evaluation tool needs to be modified in accordance with thesize and the resolution of the touch panel included in mobile terminals.

For example, in the case where a resolution of a touch panel of a mobileterminal is different, there is a possibility that at least one of thehorizontal coordinate and the vertical coordinate of an icon located inthe touch panel is different. Therefore, in the case where a process isperformed in which the same application is run and the area is specifiedby coordinates when specifying an area for an icon to be selected, theremay be a different area specified.

It is an object of the present invention, in order to solve the aboveproblems, regardless of the device included in a mobile terminal, totest functions performed by software installed in the mobile terminal.

Means for Solving the Problem

The present testing apparatus is implemented as a testing apparatus forevaluating operations performed by software installed in a mobileterminal, including a scenario setting unit configured to set a scenarioincluding operation information for performing functions to be executedby the mobile terminal, an operation determining unit configured todetermine whether an operation indicated by the operation informationincluded in the scenario set by the scenario setting unit is influencedor not by the device installed in the mobile terminal, an operationtarget converting unit configured to convert an operation determined tobe influenced by the device installed in the mobile terminal inaccordance with the device installed in the mobile terminal, a scenarioexecution unit configured to execute a scenario set by the scenariosetting unit based on the operation converted by the operation targetconverting unit, and a scenario execution result determining unitconfigured to determine whether an execution result of the scenarioexecuted by the scenario execution unit is the same as a result assumedin advance.

The operation determining unit may be configured to determine that theoperation is influenced by the device installed in the mobile terminalin the case where at least one of a screen-push operation and akey-press operation is included in the operation indicated by theoperation information included in the scenario set by the scenariosetting unit.

The operation target converting unit may be configured to calculate therange of the coordinates for executing at least one of a screen-pushoperation and a key-press operation by analyzing the information of thescreen displayed by the mobile terminal in the case where the at leastone of the screen-push operation and the key-press operation is includedin the operation that is determined by the operation determining unit tobe influenced by the device installed in the mobile terminal.

The operation target converting unit may be configured to analyze theinformation of the screen obtained by a function installed in the mobileterminal for obtaining the information of the screen.

The operation determining unit may be configured to determine that theoperation is influenced by the device installed in the mobile terminalin the case where an operation for executing a GPS measurement isincluded in the operation indicated by the operation informationincluded in the scenario set by the scenario setting unit.

The operation target converting unit may be configured to convert atleast one of a measurement command for executing the GPS measurement anda parameter in the case where an operation for executing the GPSmeasurement is included in the operation that is determined by theoperation determining unit to be influenced by the device installed inthe mobile terminal.

The scenario may be configured to include one or a plurality of thefunctions performed by the mobile terminal.

Also, the present invention may be configured to be a testing method ora program to be executed by the testing apparatus above.

Effect of the Present Invention

According to the disclosed embodiments of the present invention,regardless of the device included in a mobile terminal, functionsperformed by software installed in the mobile terminal can be tested.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing illustrating an example of the present embodimentsof a testing apparatus.

FIG. 2 is a drawing illustrating an example of the present embodimentsof a mobile terminal.

FIG. 3 is a drawing illustrating an example of the present embodimentsof an automated evaluation tool.

FIG. 4 is a drawing illustrating an example of the present embodimentsof a scenario.

FIG. 5 is a drawing illustrating an example of the present embodimentsof a scenario.

FIG. 6 is a drawing illustrating an example of the present embodimentsof a scenario.

FIG. 7 is a drawing illustrating an example of the present embodimentsof device dependency definition.

FIG. 8 is a drawing illustrating an example of the present embodimentsof an analysis result of screen information.

FIG. 9 is a functional block diagram illustrating an example of thepresent embodiments of a testing apparatus.

FIG. 10 is a flow chart illustrating an example of the presentembodiments of operations of a testing apparatus.

FIG. 11 is a flow chart illustrating an example of the presentembodiments of operations of a testing apparatus.

FIG. 12 is a flow chart illustrating an example of the presentembodiments of operations of a testing apparatus.

EMBODIMENTS FOR CARRYING OUT THE INVENTION

In the following, embodiments of the present invention will be describedby referring to the accompanying drawings. Note that throughout thedrawings for describing the present embodiments, the same referralnumbers are used for the same functionalities, and the repeateddescription will be omitted.

Embodiments <Testing Apparatus 100>

An automated evaluation tool of the present embodiments is installed ina PC (Personal Computer), etc. Also, the automated evaluation tool maybe installed in an apparatus for testing functions performed by softwareinstalled in a mobile terminal.

In the present embodiment, as an example, a case is described where anautomated evaluation tool is installed in a PC. By having an automatedevaluation tool installed in a PC, the PC functions as a testingapparatus 100 of a mobile terminal.

By the automated evaluation tool of a mobile terminal, scenarios relatedto operations for performing the target functions are created inadvance.

The testing apparatus 100 determines which scenario to use from thescenarios created in advance to be used for evaluating functions of amobile terminal.

The testing apparatus 100, when executing an operation for performing atarget function according to the determined scenario, determines whetherthe operation depends on a device of the mobile terminal or not. Thatis, the testing apparatus 100 determines whether the operation isinfluenced or not by the device difference. In other words, the testingapparatus 100 determines whether the operation can be the same operationor not even when the device is different. For example, in the case wherethe operation is an input for a touch panel, the operation is determinedto be influenced by the difference of the device such as the size, theresolution, etc., of the touch panel. Regarding an input for a touchpanel, the input location is assumed to be specified by the coordinates.

Also, for example, in the case where the operation is a GPS measurement,it is determined to be influenced by GPS chips, etc. There exist variouskinds of GPS chips installed in mobile terminals. The reason is that itis assumed that there are cases where different commands of GPSmeasurement or different parameters are described depending on the GPSchips because there exist various kinds of GPS chips.

In the case where it is determined that the operation is influenced bythe device difference, the testing apparatus 100 converts the operationcontents to fit the device.

The testing apparatus 100 executes the operation for performing thetarget function based on the determined scenario, and determines whetherthe result of the executed operation is correct or not.

FIG. 1 shows an example of the present embodiments of the testingapparatus 100 in which the automated evaluation tool is stored.

The testing apparatus 100 includes a microprocessor (MPU:Micro-Processing Unit) 102, a memory unit 104, an input unit 106, and anoutput unit 108. The MPU 102, the memory unit 104, the input unit 106and the output unit 108 are connected by a bus 150.

The MPU 102 controls the memory unit 104, the input unit 106 and theoutput unit 108. The MPU 102 functions according to the program storedin the memory unit 104, and performs a certain process.

In the memory unit 104, an application, an Operating System (OS) and anautomated evaluation tool are stored. For example, the memory unit 104is an external memory device that stores data and programs in acomputer. The memory unit 104 includes, for example, a hard disk (fixeddisk), a flexible disk, an MO (Magneto-Optical disk), CD-R (Compact DiskRecordable), and a magnetic tape. The application is software thatincludes functions performing tasks to be executed on the testingapparatus 100 by the user. For example, the application includes a wordprocessor, spreadsheet software, a database management system (DBMS),and a media player. The Operating System is software that provideshardware-abstracted interfaces to the application software in thetesting device 100. The automated evaluation tool is a tool forevaluating at least one of software quality or software functionality bycausing software installed in the mobile terminal to operate byoperating the mobile terminal on behalf of the user.

The input unit 106 is configured with, for example, a keyboard or amouse, and sends instructions to the testing device 100 or performs datainput. Also, the input unit 106 may be configured with a touch panel.The instructions to the testing device 100 include instructions for theoperating system, instructions for the application, and instructions forthe automated evaluation tool.

The output unit 108 is configured with, for example, a display, anddisplays a process status and a process result of the testing device100. The process status and the process result includes those of theOperating System, the application and the automated evaluation tool. Thedisplay includes a liquid crystal display, a CRT (Cathode Ray Tube)display, a plasma (PDP: Plasma Display Panel) display, an organic EL(Electro-Luminescence) display, etc.

<Mobile Terminal 200>

The mobile terminal 200 includes an input device such as a touch panel,etc. By having the touch panel operated by the user, the mobile terminal200 performs predefined functions.

FIG. 2 illustrates a present embodiment of the mobile terminal 200.

The mobile terminal 200 includes a display screen 202. On the displayscreen 202, one or a plurality of icons 204 ₁ through 204 ₆ aredisplayed. In an example illustrated in FIG. 2, six icons are shown, butthe number of icons can be 1 to 5, or can be equal to or more than 7. Byhaving the user pressing any of the icons 204 ₁ through 204 ₆, afunction corresponding to the pressed icon is performed.

Furthermore, the mobile terminal 200 includes a “menu key 206”, a “homekey 208”, and a “back key 210”. By having any one of a “menu key 206”, a“home key 208”, and a “back key 210” pressed, a function correspondingto the pressed key is performed.

<An Example of a Configuration of a Testing System>

In a testing system, the mobile terminal 200 and the testing apparatus100 are connected. For example, the mobile terminal 200 and the testingapparatus 100 may be connected by a cable (not shown in the figure). Itis preferable that the mobile terminal 200 includes a user interface(UI) for accepting an operation of a user. For example, the UI includesa touch panel, etc. Also, the mobile terminal 200 may not need toinclude the UI if it can change the internal operation by an electricsignal. For example, the mobile terminal 200 may be of a card type, orof a module type.

Also, the testing system may be equipped with a camera for takingpictures displayed on the display screen 202 of the mobile terminal 200.The camera takes at least one of a picture and a moving picturedisplayed on the display screen 202 of the mobile terminal 200. The atleast one of the picture and the moving picture displayed on the displayscreen 202 taken by the camera is inputted to the testing device 100.For example, by connecting between the camera and the testing device 100with a cable (not shown in the figure), the at least one of the pictureand the moving picture may be transmitted and received between thecamera and the testing device 100 via the cable.

<Automated Evaluation Tool>

FIG. 3 shows an example of a configuration of the automated evaluationtool.

The automated evaluation tool includes a key operation driver. The keyoperation driver is software for providing the MPU 102 that functions asthe Operating System with an interface to the mobile terminal 200.

The automated evaluation tool includes an automated evaluation engine.The automated evaluation engine is software for the MPU 102 thatfunctions as the automated evaluation tool to perform a function toevaluate software installed in the mobile terminal 200.

The automated evaluation tool includes an OCR (Optical CharacterReader). The OCR optically reads a character from a picture that istaken from a part or the whole of what is displayed on the displayscreen 202 of the mobile terminal 200, and identifies the character byreferring to a pattern stored in advance. The OCR may be an OCR thatoptically reads a character from a moving picture that is taken from apart or the whole of what is displayed on the touch panel of the mobileterminal 200, and identifies the character by referring to a patternstored in advance.

Also, in the automated evaluation tool, an image recognizing functionmay be installed.

At least one of a picture and a moving picture may be obtained by afunction included in the mobile terminal 200. The function for obtainingat least one of a picture and a moving picture included in the mobileterminal 200 may be a screenshot, a screen dump, or a screen capture.The screenshot is data that record a display on the display screen in auniversal format such as BMP (Bit Map), PNG (Portable Network Graphics),JPEG (Joint Photographic Experts Group), etc. The screen dump isinternal data obtained temporarily by a XWD (X Window Dump), etc. Thescreen capture is data that record the changing of the screen as amoving picture.

<Scenario for Testing>

The automated evaluation tool includes a scenario for testing. Thescenario for testing is a scenario in which a procedure of operations tobe executed by the mobile terminal 200 is indicated when a function isevaluated by the automated evaluation tool. For example, the scenariofor testing is created by running the automated evaluation tool.

FIG. 4 is a drawing illustrating an example of the scenario for testing.In FIG. 4, as examples, two scenarios (scenario 1 and scenario 2) areshown. A scenario may be prepared for each application that runs whenevaluating functions of the mobile terminal 200. To be more precise, anemail transmission, an outgoing telephone call, an outgoing packet call,a usage of a paid service, a connection to a Web page, etc., areincluded.

When a scenario for testing is created, a name for defining a scenario(scenario name) is created. For example, as scenario names, “scenario 1”and “scenario 2” are created.

Furthermore, for each scenario, an “operation” for indicating a key thatis an operation target for executing the scenario and a “command” forindicating a flow of the key are described. For example, in the scenarioindicated by the scenario name “scenario 1”, information indicating keysto be operated (“operation 1”, . . . , “operation n”) and commands forcontrolling the operation procedure of the keys to be operated (“command1”, . . . , “command m”) are included. The “operation” is associatedwith the name of a part of an operation target. To be more precise, thepart of an operation target includes a touch panel and buttons. Also,the part of an operation target may include a measurement command, aparameter, etc.

FIG. 5 shows a present embodiment of the scenario. In FIG. 5, operationsof scenario 1 are shown.

The “operation” included in the scenario 1 includes a “screen push”, andthe operation target associated with the “screen push” includes a“button 1”. Likewise, The “operation” includes “key press”, and theoperation target associated with the “key press” includes a “menu key”.The “operation” includes “screen push”, and the operation targetassociated with the “screen push” includes a “button 2”. Also, not shownin the figure, the “operation” includes “GPS measurement”, and theoperation target associated with the “GPS measurement” includes a“measurement command” or a “parameter”.

What is shown in FIG. 5 is an example and can be changed as needed.

Also, in the scenario indicated by the scenario name “scenario 2”,information indicating keys to be operated (“operation 1”, . . . ,“operation x”) and commands for controlling the operation procedure ofthe keys to be operated (“command 1”, . . . , “command y”) are included.

Also, a plurality of the scenarios may be put together to define asingle scenario. For example, a plurality of the scenarios for anevaluation target may be put together to define a single new scenario.

FIG. 6 illustrates an example in which a plurality of the functions areput together to be defined as a single new function.

In an example shown in FIG. 6, a plurality of the scenarios (“scenarioX”, “scenario Y”, “scenario Z”) are put together to be defined as asingle new scenario (“scenario 1”). In other words, in the “scenario 1”,the plurality of the scenarios (“scenario X”, “scenario Y”, . . . ,“scenario Z”) are nested.

<Device Dependency Determining Process>

It is determined by the automated evaluation tool whether an operationfor executing a function of an evaluation target depends on the deviceor not.

FIG. 7 shows an example of the present embodiment of a device dependencydefinition that is used when it is determined by the automatedevaluation tool whether an operation for executing a function of anevaluation target depends on the device or not.

In an example shown in FIG. 7, information indicating an operation andinformation indicating an existence or a non-existence of devicedependency are stored, the information indicating an operation beingassociated with the information indicating an existence or anon-existence of device dependency. To be more precise, regarding the“screen push” operation, because the pushed location varies depending onthe device, the device dependency is set as “yes”. Regarding the “keypress” operation, because the location to be pressed varies depending onthe device, the device dependency is set as “yes”. Regarding the “GPSmeasurement” operation, because the a measurement command of the “GPSmeasurement” and a parameter vary depending on the device, the devicedependency is set as “yes”. Regarding the “email delivery confirmation”operation, because it is assumed that there is no influence from thedevice difference, the device dependency is set as “no”. Regarding the“application update” operation, because it is assumed that there is noinfluence from the device difference, the device dependency is set as“no”.

What is shown in FIG. 7 is an example and can be set as needed. Thedevice dependency may be set for other operations.

<Operation Target Conversion Process>

In the case where it is determined that an operation for performing afunction of an evaluation target depends on the device as a result ofdetermination by the automated evaluation tool, an operation targetconversion process is performed.

Here, it will be described for the case where the operation that isdetermined to depend on the device is a “screen push” or a “key press”.For other cases, the operation content will be converted so as to fitthe device.

Screen information is obtained by the automated evaluation tool. To bemore precise, a picture of the display screen 202 of the mobile terminal200 described referring to FIG. 2 is obtained. The picture of thedisplay screen may be obtained by a camera or by a function included inthe mobile terminal 200.

The screen information is analyzed by the automated evaluation tool. Tobe more precise, locations of a plurality of icons included in thedisplay screen are recognized. For example, the locations may berecognized by an image recognizing function.

The coordinates of the locations of the recognized icons are calculatedby the automated evaluation tool. The automated evaluation toolassociates a function to be executed by pressing the icon with thecoordinates of the location of the icon. To be more precise, thefunction to be executed by pressing the icon may be identified byrecognizing the image of the icon itself. When the function to beexecuted by pressing the icon is identified, in order to recognizecharacters included in the icon, OCR may be used.

FIG. 8 is an example of an analysis result of the screen information.

In FIG. 8, the name of the icon obtained by analyzing the screeninformation, information indicating the layer of the function to beexecuted by operating the icon, a type of the icon and informationindicating the location of the icon are stored.

The part to become an operation target associated with the “operation”included in the scenario is associated with the coordinates by theautomated evaluation tool.

By having the information indicating the location of the icon calculatedin accordance with the device by the automated evaluation tool,regardless of the device included in the mobile terminal 200, the icon'slocation that should be specified at the time of evaluation can beconverted.

Also, the measurement command and the parameters at the time of GPSmeasurement are converted by the automated evaluation tool. By havingthe measurement command and the parameters converted, regardless of thedevice (GPS chip) included in the mobile terminal 200, the measurementcommand and the parameters can be converted to fit the device.

<Functions of the Automated Evaluation Tool>

FIG. 9 is a functional block diagram indicating an embodiment of thepresent invention of the testing apparatus 100. In FIG. 9, functionsmainly executed by the MPU 102 according to the automated evaluationtool stored in the memory unit 104 are shown.

The testing apparatus 100 includes a scenario selecting unit 1022. Thescenario selecting unit 1022 selects a scenario to be executed by themobile terminal 200. For example, the scenario selecting unit 1022 mayselect a scenario to be executed by the mobile terminal 200 from aplurality of the scenarios set in advance. The scenario selecting unit1022 inputs information indicating the selected scenario to a devicedependency determining unit 1024.

The testing apparatus 100 includes the device dependency determiningunit 1024. The device dependency determining unit 1024 is connected tothe scenario selecting unit 1022. The device dependency determining unit1024 determines whether an operation included in the scenario selectedby the scenario selecting unit 1022 depends on the device or not. To bemore precise, the device dependency determining unit 1024 determines,referring to the device dependency definition shown in FIG. 7, whetheroperations included in the scenario include an operation that depends onthe device or not. The device dependency determining unit 1024 inputsinformation indicating operations that depend on the device to anoperation target converting unit 1026. The device dependency determiningunit 1024 inputs information indicating operations that don't depend onthe device to a scenario executing unit 1028.

The testing apparatus 100 includes the operation target converting unit1026. The operation target converting unit 1026 is connected to thedevice dependency determining unit 1024. The operation target convertingunit 1026 converts an operation target so that it will fit the deviceinstalled in the mobile terminal 200 of the evaluation target based onthe information from the device dependency determining unit 1024indicating an operation that depends on the device. To be more precise,the coordinates of the icon may be converted in accordance with the sizeof the touch panel of the mobile terminal 200. Also, the measurementcommand and parameters at the time of GPS measurement may be converted.The operation target converting unit 1026 inputs to the scenarioexecuting unit 1028 information indicating the operation whose operationtarget is converted.

The testing apparatus 100 includes the scenario executing unit 1028. Thescenario executing unit 1028 is connected to the device dependencydetermining unit 1024 and the operation target converting unit 1026. Thescenario executing unit 1028 executes the scenario selected by thescenario selecting unit 1022. When the scenario selected by the scenarioselecting unit 1022 is executed, operations determined to not depend onthe device by the device dependency determining unit 1024 and operationswhose operation target is converted by the operation target convertingunit 1026 in accordance with the device are executed. The scenarioexecuting unit 1028 inputs an execution result of the scenario to ascenario execution result determining unit 1030.

The testing apparatus 100 includes the scenario execution resultdetermining unit 1030. The scenario execution result determining unit1030 is connected to the scenario executing unit 1028. The scenarioexecution result determining unit 1030 determines whether the executionresult of the scenario is the same as a result assumed in advance basedon the execution result of the scenario inputted by the scenarioexecuting unit 1028. In the case where the execution result of thescenario is the same as the result assumed in advance, the scenarioexecution is determined to be a success. On the other hand, in the casewhere the execution result of the scenario is different from the resultassumed in advance, the scenario execution is determined to be afailure. The scenario execution result determining unit 1030 reflectsthe execution result of the scenario in execution result information. Inthe execution result information, the number of execution failures ofthe scenario is stored for each scenario.

<Operations of the Testing Apparatus>

FIG. 10 illustrates an example of the present embodiment of operationsof the testing apparatus 100.

The testing apparatus 100 selects a scenario (step S1002). A pluralityof the scenarios may be selected. For example, the scenario selectingunit 1022 selects one of the scenarios.

The testing apparatus 100 determines whether an operation included inthe scenario selected at step S1002 depends on the device. That is, thedevice dependency determining unit 1024 refers to the device dependencydefinition and determines whether the operation included in the scenariodepends on the device. In the case where a plurality of the operationsare included in the scenario, it is determined for each of theoperations whether the operation depends on the device.

In the case where the operation depends on the device (step S1004: YES),the testing apparatus 100 converts the operation target in accordancewith the device (step S1006). That is, in the case where the operationincluded in the scenario depends on the device, the operation targetconverting unit 1026 converts the target of the operation that dependson the device to fit the device.

After the operation target is converted to fit the device, or in thecase where the operation is not determined to depend on the device (stepS1004: NO), the testing apparatus determines whether the determinationof whether the operation depends on the device is finished for all theoperations (step S1008).

In the case where the determination for all operations is not finished(step S1008: NO), the step returns to step S1004. The testing apparatus100 performs step S1004 through step S1006 for operations for which thedetermination of the device dependency is not finished.

In the case where the determination for all operations is finished (stepS1008: YES), the testing apparatus 100 executes the scenario (stepS1010). That is, the scenario executing unit 1028 executes the scenario.

The testing apparatus 100 determines the execution result of thescenario (step S1012). For example, the scenario execution resultdetermining unit 1030 determines whether the execution result of thescenario is a success by determining whether the execution result of thescenario is the same as the result assumed in advance.

After the determination of the execution result of the scenario at stepS1012, the step returns to step S1002.

The program causing the MPU 102 to function as the testing apparatus 100is provided in the stored state in a recording medium such as a flexibledisk, a CD-ROM, a memory card, etc. Also, the program may be downloaded.When the recording medium is inserted into an auxiliary storage deviceof a computer, the program stored in the recording medium is read. TheMPU 102 writes the read program onto an RAM or an HDD, and performs theprocesses. The program causes the computer to perform the processes ofstep S1002 through S1012 of FIG. 10. Also, for example, the program maycause the computer to perform at least a portion of the processes.

<Details of the Device Dependency Checking Process>

FIG. 11 shows the detailed operations executed by the device dependencydetermining unit 1024.

The device dependency determining unit 1024 determines whether thedevice dependency associated with the operation included in the scenariois “YES” (step S1102).

In the case where the device dependency is “YES” (step S1102: YES), thedevice dependency determining unit 1024 recognizes that the operation isdevice dependent. (step S1104).

The device dependency determining unit 1024 associates the targetoperation included in the scenario with information indicating that thedevice dependency is “YES” and records them (step S1106).

In the case where the device dependency is not “YES” (step S1102: NO),the device dependency determining unit 1024 recognizes that theoperation is not device dependent (step S1108).

The program causing the MPU 102 to function as the device dependencydetermining unit 1024 is provided in the stored state in a recordingmedium such as a flexible disk, a CD-ROM, a memory card, etc. Also, theprogram may be downloaded. When the recording medium is inserted into anauxiliary storage device of a computer, the program stored in therecording medium is read. The MPU 102 writes the read program onto anRAM or an HDD, and performs the process. The program causes the computerto perform the processes of step S1102 through S1108 of FIG. 11. Also,for example, the program may cause the computer to perform at least aportion of the processes.

<Details of the Operation Target Converting Process>

FIG. 12 shows the detailed operations executed by the operation targetconverting unit 1026. In FIG. 12, an example in which coordinates of anicon are converted in accordance with the size of the touch panel of themobile terminal 200 is shown.

The operation target converting unit 1026 obtains information indicatingthe operation target (step S1202). The operation target converting unit1026 obtains from the device dependency determining unit 1024information indicating the operation target associated with theoperation that is determined to be device dependent.

The operation target converting unit 1026 analyzes the output screen(step S1204). The operation target converting unit 1026 obtains andanalyzes a picture displayed on the display screen 202 of the mobileterminal 200. To be more precise, the operation target converting unit1026 analyzes location information of an icon included in a picturedisplayed on the display screen 202.

The operation target converting unit 1026 calculates the coordinatesbased on the result of the screen analysis (step S1206). The operationtarget converting unit 1026 converts the location information of theicon included in the picture displayed on the display screen 202 intocoordinates.

The operation target converting unit 1026 outputs the coordinateinformation (step S1208). The operation target converting unit 1026inputs the coordinate information to the scenario executing unit 1028.

The program causing the MPU 102 to function as the operation targetconverting unit 1026 is provided in the stored state in a recordingmedium such as a flexible disk, a CD-ROM, a memory card, etc. Also, theprogram may be downloaded. When the recording medium is inserted into anauxiliary storage device of a computer, the program stored in therecording medium is read. The MPU 102 writes the read program onto anRAM or an HDD, and performs the process. The program causes the computerto perform the processes of step S1202 through S1208 of FIG. 12. Also,for example, the program may cause the computer to perform at least aportion of the processes.

In the present embodiment described above, as an example of a devicedependent operation, a “push-screen operation” and a “key-pressoperation” are shown, and are applied to operations specificallyutilizing coordinates.

Also, an operation target may be changed depending on a sensor installedin the mobile terminal 200. To be more precise, the operation target maybe changed in accordance with the sensitivity or the temperature of thesensor.

According to the present embodiment, regardless of the device includedin a mobile terminal, functions installed in the mobile terminal can beevaluated.

A testing apparatus and a testing method according to the presentembodiments are described above, but the present invention is notlimited to the above embodiments, and various modifications andrefinements may be made without departing from the scope of the presentinvention.

For the sake of convenience, the present embodiments are described usingspecific numbers in order to facilitate understanding of the invention,but these numbers are used just as examples and, unless otherwise noted,any appropriate number can be used. For the sake of convenience, devicesof the present embodiments are described using a functional blockdiagram, but those devices may be realized as hardware, software, or acombination of both.

The present application is based on and claims the benefit of priorityof Japanese Priority Application No. 2011-256422 filed on Nov. 24, 2011the entire contents of which are hereby incorporated by reference.

DESCRIPTION OF THE REFERENCE NUMERALS

-   -   100 Testing apparatus    -   102 MPU    -   104 Memory unit    -   106 Input unit    -   150 Bus    -   200 Mobile terminal    -   202 Display screen    -   204 _(n) (n is an integer, n>0) Icon    -   206 Menu key    -   208 Home key    -   210 Back key    -   1022 Scenario selecting unit    -   1024 Device dependency determining unit    -   1026 Operation target converting unit    -   1028 Scenario executing unit    -   1030 Scenario execution result determining unit

1. A testing apparatus for evaluating operations by software installedin a mobile terminal, the testing apparatus comprising: a scenariosetting unit configured to set a scenario including operationinformation for executing functions that are performed by the mobileterminal, an operation determining unit configured to determine whetheran operation indicated by the operation information included in thescenario set by the scenario setting unit is influenced by a deviceinstalled in the mobile terminal, an operation target converting unitconfigured to convert the operation determined to be influenced by thedevice installed in the mobile terminal by the operation determiningunit in accordance with the device installed in the mobile terminal, ascenario executing unit configured to execute the scenario set by thescenario setting unit according to the operation converted by theoperation target converting unit, and a scenario execution resultdetermining unit configured to determine whether an execution result ofthe scenario executed by the scenario execution unit is the same as aresult assumed in advance.
 2. The testing apparatus as claimed in claim1, wherein in the case where at least one of a screen-push operation anda key-press operation is included in the operation indicated by theoperation information included in the scenario set by the scenariosetting unit, the operation determining unit determines that theoperation is influenced by the device installed in the mobile terminal.3. The testing apparatus as claimed in claim 2, wherein in the casewhere at least one of the screen-push operation and the key-pressoperation is included in the operation determined to be influenced bythe device installed in the mobile terminal by the operation determiningunit, the operation target converting unit calculates a range ofcoordinates for executing at least one of the screen-push operation andthe key-press operation by analyzing information of a screen displayedon the mobile terminal.
 4. The testing apparatus as claimed in claim 3,wherein the operation target converting unit analyzes the information ofthe screen obtained by a function for obtaining the information of thescreen, installed in the mobile terminal.
 5. The testing apparatus asclaimed in claim 1, wherein in the case where an operation forperforming a GPS measurement is included in the operation indicated bythe operation information included in the scenario set by the scenariosetting unit, the operation determining unit determines that theoperation is influenced by the device installed in the mobile terminal.6. The testing apparatus as claimed in claim 5, wherein in the casewhere the operation for performing the GPS measurement is included inthe operation determined to be influenced by the device installed in themobile terminal by the operation determining unit, the operation targetconverting unit converts at least one of a measurement command and aparameter for performing the GPS measurement.
 7. The testing apparatusas claimed in claim 1, wherein the scenario includes one or a pluralityof the functions to be performed by the mobile terminal.
 8. A testingmethod in a testing apparatus for evaluating operations by softwareinstalled in a mobile terminal, the testing method comprising: ascenario setting step of setting a scenario including operationinformation for executing functions that are performed by the mobileterminal, a operation determining step of determining whether anoperation indicated by the operation information included in thescenario set by the scenario setting unit is influenced by a deviceinstalled in the mobile terminal, an operation target converting step ofconverting the operation determined to be influenced by the deviceinstalled in the mobile terminal by the operation determining unit inaccordance with the device installed in the mobile terminal, a scenarioexecuting step of executing the scenario set by the scenario settingunit according to the operation converted by the operation targetconverting unit, and a scenario execution result determining step ofdetermining whether an execution result of the scenario executed by thescenario execution unit is the same as a result assumed in advance.